Skip to content

Conversation

cgwalters
Copy link
Contributor

I want to use this for the same reason as
rust-lang/rust#81822
was added to std. While it's currently unstable, I can't imagine
it would change.

Copy link
Member

@sunfishcode sunfishcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

cap-std usually puts features corresponding to unstable features in std behind a config option, however in this case, I think it's reasonable to just provide these. As you say, it's unlikely that these will change before stabilization, and they're useful.

Please add comments to the cap-std versions mentioning that the std version is not yet stabilized though, with a link to the tracking issue. And please add comments to the cap-async-std versions mentioning that cap-async-std doesn't have these operations yet.

I want to use this for the same reason as
rust-lang/rust#81822
was added to std.  While it's currently unstable, I can't imagine
it would change.
@cgwalters
Copy link
Contributor Author

OK, comments should be addressed!

Copy link
Member

@sunfishcode sunfishcode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! Thanks for your patience in porting this to the cap-async-std and fs_utf8 variants :-).

@sunfishcode sunfishcode merged commit 16a7dae into bytecodealliance:main Feb 11, 2022
@sunfishcode
Copy link
Member

This is now released in 0.24.2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants